Don't panic for other region physaddr handling in vcpu_translate
authordjm@kirby.fc.hp.com <djm@kirby.fc.hp.com>
Wed, 9 Nov 2005 21:31:01 +0000 (15:31 -0600)
committerdjm@kirby.fc.hp.com <djm@kirby.fc.hp.com>
Wed, 9 Nov 2005 21:31:01 +0000 (15:31 -0600)
xen/arch/ia64/xen/vcpu.c

index 4e80bc16a1caf7503837abe28a2b0157b203a195..1f0a19cb6b36dd3bc5603bdfcacb28409e113483 100644 (file)
@@ -1299,7 +1299,10 @@ IA64FAULT vcpu_translate(VCPU *vcpu, UINT64 address, BOOLEAN is_data, UINT64 *pt
                unsigned long region = address >> 61;
                // dom0 may generate an uncacheable physical address (msb=1)
                if (region && ((region != 4) || (vcpu->domain != dom0))) {
-                       panic_domain(vcpu_regs(vcpu),
+// FIXME: This seems to happen even though it shouldn't.  Need to track
+// this down, but since it has been apparently harmless, just flag it for now
+//                     panic_domain(vcpu_regs(vcpu),
+                       printk(
                         "vcpu_translate: bad physical address: %p\n",address);
                }
                *pteval = (address & _PAGE_PPN_MASK) | __DIRTY_BITS | _PAGE_PL_2 | _PAGE_AR_RWX;